Skip to main content

2. Plan-to-Plan

Intent

The Plan-to-Plan is how the MPC Chief (MPCC) commands the planning effort. It is a 30-80% solution that organizes how the MPC will complete the planning work, prevents uncontrolled planning, and ensures the Tactical Mission Plan (TMP) develops in a deliberate, synchronized manner.

2.1. Outline MPOs/MPTs​

Purpose

Similar to how TOs/TTs guide a Mission Element's (ME) execution, the MPCC must create Mission Planning Objectives (MPOs) and Mission Planning Tasks (MPTs) to effectively guide the MPC's planning.

  • MPOs describe the required planning end states that must exist for the TMP to be considered complete and executable.
  • MPTs are discrete planning actions assigned to planning LOEs to achieve an MPO.

2.1.1. Develop Planning Objectives​

  • Divide the required planning work into functional objectives as MPOs

    NOTE: Ideally, most of the MPOs align with the functional planning LOEs

  • MPO characteristics:
    • Define required planning end conditions
    • Are outcome-focused and assessable
    • Status is determined by MPT completion and integration
    • Have a tangible output artifact
  • Each MPO must have tangible output or products
Example
## MISSION PLANNING OBJECTIVES (MPOs)
- MPO-1: Perform FMA-C to identify MRT-C and KT-C
- MPO-2: Develop the CVA/H Deployment Plan
- MPO-3: Develop Host Agent Deployment + Data Collection Plans
- MPO-4: Identify and Characterize Potential Threats
- MPO-5: Develop the Threat Hunt Plan
- MPO-6: Develop the Execution Framework
- MPO-7: Develop Communication Contracts
- MPO-8: Establish Logistics Coordination
- MPO-9: Provide Intelligence Support to Planning
- MPO-10: Conduct the ROC Drill and Refine the Plan
- MPO-11: Integrate and Finalize the Tactical Mission Plan (TMP)

2.1.2. Develop Planning Tasks​

  • For each MPO, outline the discrete tasks that are required for the MPC to achieve it
  • MPT characteristics:
    • They outline the planning work that must be done to achieve the supported MPO
    • Are directly assigned to planning LOEs
    • Produce or update a tangible planning output
    • Directly support one or more MPOs
Example
## MISSION PLANNING OBJECTIVES (MPOs)
- MPO-1: Perform FMA-C to identify MRT-C and KT-C
    - MPT-1.1: Define the supported mission's purpose, method, and goals
    - MPT-1.2: Identify METs, MEFs, and associated TCAs
    - MPT-1.3: Identify critical information flows enabling MEFs
    - MPT-1.4: Identify Unacceptable Losses (ULs) and associated cyber hazards
    - MPT-1.5: Identify and distinguish KT-C and MRT-C assets
    - MPT-1.6: Prioritize MRT-C and KT-C assets by mission impact

- MPO-2: Develop the CVA/H Deployment Plan
    - MPT-2.1: Collect and validate logical and physical network architecture
    - MPT-2.2: Identify MRT-C boundaries, aggregation points, and monitoring choke points
    - MPT-2.3: Identify infrastructure device capabilities and integration constraints
    - MPT-2.4: Identify physical installation requirements and hardware needs
    - MPT-2.5: Determine DIP Sensor monitoring methods and optimal placement strategy
    - MPT-2.6: Develop the DIP Sensor Deployment Plan and translate to executable TTs

- MPO-3: Develop Host Agent Deployment + Data Collection Plans
    - MPT-3.1: Analyze targeted threat TTPs to determine required host data sources
    - MPT-3.2: Map required data components to CVA/H capabilities and identify gaps
    - MPT-3.3: Identify endpoints and log sources requiring collection configuration
    - MPT-3.4: Develop Host Agent deployment, log forwarding, and data collection plans
    - MPT-3.5: Validate collection coverage across MRT-C assets
    - MPT-3.6: Translate deployment and collection plans into executable TTs

- MPO-4: Identify and Characterize Potential Threats
    - MPT-4.1: Identify mission-relevant threat actors and associated capabilities
    - MPT-4.2: Identify relevant adversary TTPs, tools, infrastructure, and indicators
    - MPT-4.3: Develop adversary concept sketch targeting MRT-C and KT-C
    - MPT-4.4: Assess MLECOA and MDECOA against mission dependencies
    - MPT-4.5: Identify detection and response implications
    - MPT-4.6: Produce threat brief to inform planning and execution

- MPO-5: Develop the Threat Hunt Plan
    - MPT-5.1: Develop prioritized hunt hypotheses based on threat COAs
    - MPT-5.2: Identify required data sources and validate availability
    - MPT-5.3: Develop detection logic and analytic approach
    - MPT-5.4: Identify investigative pivots and escalation criteria
    - MPT-5.5: Sequence hunt activities by priority
    - MPT-5.6: Translate hunt plan into executable TTs  

- MPO-6: Develop the Execution Framework
    - MPT-6.1: Define execution LOEs grouped by functional area
    - MPT-6.2: Define MINFOR crew positions and assign roles
    - MPT-6.3: Assign TTs to execution LOEs
    - MPT-6.4: Sequence TTs and resolve task dependencies
    - MPT-6.5: Define execution phases and transition criteria
    - MPT-6.6: Develop integrated execution timeline with triggers and decision points

- MPO-7: Develop Communication Contracts
    - MPT-7.1: Identify required stakeholders
    - MPT-7.2: Define supported/supporting relationships
    - MPT-7.3: Establish communication methods and redundancies
    - MPT-7.4: Define reporting formats, frequency, and escalation thresholds
    - MPT-7.5: Establish battle rhythm events
    - MPT-7.6: Document communication contracts in the TMP

- MPO-8: Establish Logistics Coordination
    - MPT-8.1: Coordinate personnel movement, access, and facility support
    - MPT-8.2: Confirm equipment shipping, installation, and sustainment requirements
    - MPT-8.3: Validate power, rack space, environmental, and physical security support
    - MPT-8.4: Coordinate network access approvals and authorizations
    - MPT-8.5: Establish logistics POCs
    - MPT-8.6: Document logistics constraints in the TMP

- MPO-9: Provide Intelligence Support to Planning
    - MPT-9.1: Identify PIRs aligned to mission objectives
    - MPT-9.2: Collect and analyze mission-relevant threat intelligence
    - MPT-9.3: Refine MLECOA and MDECOA assessments
    - MPT-9.4: Identify intelligence-driven detection priorities
    - MPT-9.5: Collect and track RFIs generated by the MPC
    - MPT-9.6: Integrate intelligence updates into planning products

- MPO-10: Conduct the ROC Drill and Refine the Plan
    - MPT-10.1: Execute a full ROC drill by phase, LOE, and crew position
    - MPT-10.2: Validate task sequencing, triggers, dependencies, and decision points
    - MPT-10.3: Identify friction points, timing conflicts, and resource contention
    - MPT-10.4: Identify unresolved assumptions impacting execution
    - MPT-10.5: Develop contingency TTs tied to assumption failure and adverse conditions
    - MPT-10.6: Update the execution framework based on ROC findings

- MPO-11: Integrate and Finalize the Tactical Mission Plan (TMP)
    - MPT-11.1: Consolidate MPC outputs into a unified TMP framework
    - MPT-11.2: Validate consistency across LOEs, TTs, phasing, triggers, and contingencies
    - MPT-11.3: Develop and deliver the Mission Brief (ME3PC2 format) for Mission Commander approval
    - MPT-11.4: Incorporate Mission Commander feedback and approval decisions
    - MPT-11.5: Finalize the TMP in the format required by the final approval authority
    - MPT-11.6: Produce the execution-ready TMP package for the Mission Element

2.2. Outline Planning LOEs​

Purpose

Planning Lines of Effort (LOEs) organize the MPC's work into functional areas and:

  • Prevent overlap and duplication of effort
  • Provide clear ownership of planning work
  • Enable parallel planning
  • Allow the MPCC to track progress and integration
  • Are assigned MPTs in order to collectively achieve MPOs.

2.2.1. Define Planning LOEs​

  • Define planning LOEs based on the mission and required MPOs
  • Planning LOEs should:
    • Reflect functional groupings of planning work
    • Enable parallel development and later integration
  • Each planning LOE must have:
    • A single accountable lead
    • Defined integration touchpoints
    • A clearly defined functional focus
    • Identified supporting members
  • Planning LOEs may also be formed/disbanded based on specific points within the MPC timeline
Example
## PLANNING LOEs
- FMA-C
- CVA/H Deployment
- Data Collection
- Hunt Planning
- Intel Support
- Logistics

2.2.2. Assign MPTs to LOEs​

  • Assign each MPT to a specific LOE and ensure:
    • MPTs are distributed logically across LOEs by function area
    • Each MPT maps to exactly one LOE and at least one MPO
    • Cross-LOE dependencies are identified early
    • Integration requirements are visible
    • Workload is balanced

NOTE: If an MPT does not have clear LOE ownership, planning accountability is lost

Example
## PLANNING LOEs / MPT ASSIGNMENT
- LOE: FMA-C
    - [ ] MPT-1.1
    - [ ] MPT-1.2
    - [ ] MPT-1.3
    - [ ] MPT-1.4
    - [ ] MPT-1.5
    - [ ] MPT-1.6

- LOE: CVA/H Deployment
    - [ ] MPT-2.1
    - [ ] MPT-2.2
    - [ ] MPT-2.3
    - [ ] MPT-2.4
    - [ ] MPT-2.5
    - [ ] MPT-2.6

- LOE: Intel Support
    - [ ] MPT-4.1
    - [ ] MPT-4.2
    - [ ] MPT-4.3
    - [ ] MPT-4.4
    - [ ] MPT-4.5
    - [ ] MPT-4.6
    - [ ] MPT-9.1
    - [ ] MPT-9.2
    - [ ] MPT-9.3
    - [ ] MPT-9.4
    - [ ] MPT-9.5
    - [ ] MPT-9.6

2.3. Establish the MPC Timeline​

Purpose

The MPCC must impose time discipline on the planning effort and define the planning window from mission receipt to execution-ready TMP.

A structured timeline and battle rhythm:

  • Forces convergence
  • Prevents scope creep
  • Protects integration and ROC time
  • Ensures the TMP is mature before Commander approval
  • Identify the major MPC timeline anchors first:
    • MPC In-Brief / Kick-Off
      • Formal start of structured planning
      • Confirms mission understanding, MPOs/MPTs, LOEs, timeline, and expectations
      • Establishes planning priorities and suspenses
    • "How Goes It" (HGI) Checks
      • Structured progress reviews led by the MPCC
      • Assess MPO status and tangible MPT outputs
      • Identify cross-LOE friction and reset priorities
      • Enforce timeline discipline
    • LOE Integration Points
      • Consolidate LOE outputs into TMP structure
      • Resolve cross-LOE conflicts before ROC
    • "Good Idea Cut-Off Line" (GICL)
      • Predetermined point where major plan changes are no longer accepted
      • Protects stability prior to ROC
      • After GICL, only risk-driven corrections are allowed
    • ROC Drill
      • Full table-top of the plan by phase, LOE, and crew position
      • Validates sequencing, triggers, dependencies, and contingencies
      • Identifies execution friction prior to Mission Commander brief
    • Mission Commander Brief
      • Formal presentation of the completed plan (SMEAC/ME3PC2 format)
      • Confirms command approval, risk acceptance, and decision authorities
    • Product Delivery
      • Final execution-ready TMP package staged for the Mission Element
      • All annexes, task matrices, and supporting products included
  • Identify non-GICL "lock points":
    • MPO/MPT freeze (changes require MPCC approval)
    • LOE deliverable cutoffs (integration protected time)
    • Assumption/RFI cutoff for planning (late RFIs become contingencies)
  • Outline all other important timeline events affecting the MPC, such as:
    • Unique task/deliverable deadlines
    • Scheduled Intel update briefs
    • Administrative events

NOTE: The ROC drill must occur with sufficient time remaining to fix deficiencies.

Example